Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: An efficient way to update WasmEdge's version #53

Open
alabulei1 opened this issue May 1, 2023 · 10 comments
Open

Feature Request: An efficient way to update WasmEdge's version #53

alabulei1 opened this issue May 1, 2023 · 10 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@alabulei1
Copy link
Collaborator

Is your feature request related to a problem? Please describe.

When WasmEdge has released a new version, we should ensure everything in this doc uses the latest version of WasmEdge.

There are 12 files that need to be synced with the latest version of WasmEdge. It would be complex to maintain all 12 files.

Describe the solution you'd like.

Can we think of a simple way to update the version of WasmEdge? For example, we can first set a general parameter called {{ wasmedge_version }}. Then we update ``{{ wasmedge_version }}` equals the latest version of WasmEdge. Finally, all the docs are using the same and lastest version of WasmEdge.

This would be much easier to update WasmEdge's version. Any feedback is welcome.

Describe alternatives you've considered

No response

Additional context.

No response

@alabulei1 alabulei1 added enhancement New feature or request help wanted Extra attention is needed labels May 1, 2023
@kokamkarsahil
Copy link
Contributor

Can we think of a simple way to update the version of WasmEdge? For example, we can first set a general parameter called {{ wasmedge_version }}. Then we update ``{{ wasmedge_version }}` equals the latest version of WasmEdge. Finally, all the docs are using the same and lastest version of WasmEdge.

Yes it's a good approach I was thinking of a build step where it scans all files and replaces that word with a version number specified using sed[0] or other similar tool.

  1. https://www.gnu.org/software/sed/manual/sed.html

@Bhardwaj-Himanshu
Copy link

I do not have any idea about what could solution be, but am happy to help if I could!

@Sukriti-sood
Copy link
Contributor

@alabulei1 Are the docs not going to be updated for different versions/releases? If we are, then we can easily change the variable value at any time. Please correct me if I have misunderstood the feature.

@alabulei1
Copy link
Collaborator Author

Can we think of a simple way to update the version of WasmEdge? For example, we can first set a general parameter called {{ wasmedge_version }}. Then we update ``{{ wasmedge_version }}` equals the latest version of WasmEdge. Finally, all the docs are using the same and lastest version of WasmEdge.

Yes it's a good approach I was thinking of a build step where it scans all files and replaces that word with a version number specified using sed[0] or other similar tool.

  1. https://www.gnu.org/software/sed/manual/sed.html

This sounds good! A tool like this can reduce human errors

@alabulei1
Copy link
Collaborator Author

alabulei1 commented May 6, 2023

@alabulei1 Are the docs not going to be updated for different versions/releases? If we are, then we can easily change the variable value at any time. Please correct me if I have misunderstood the feature.

@hydai @juntao What do you think? I think we use this way when 1.0 is released.

@Bhardwaj-Himanshu
Copy link

Yup something like-
image
Could be very useful for onboarding developers!

@hydai
Copy link
Member

hydai commented May 6, 2023

@alabulei1 Are the docs not going to be updated for different versions/releases? If we are, then we can easily change the variable value at any time. Please correct me if I have misunderstood the feature.

@hydai @juntao What do you think? I think we use this way when 1.0 is released.

The 0.x series changes API a lot between versions, and it would be better to have it right now. As you can see here, we already split the API reference during different versions.

@kokamkarsahil
Copy link
Contributor

Just to add on:
image
Source: https://docusaurus.io/docs/versioning

The 0.x series changes API a lot between versions, and it would be better to have it right now. As you can see here, we already split the API reference during different versions.

We can tag this version for now and set disableVersioning and enable it in future.

@alabulei1
Copy link
Collaborator Author

I find how to pass env var in docusarus V2. This will fix this issue faster. https://stackoverflow.com/questions/61127010/how-to-pass-env-var-to-docusaurus-v2

@alabulei1
Copy link
Collaborator Author

alabulei1 commented Sep 11, 2023

Feature Request: An efficient way to update WasmEdge's version
#53
The central problem discussed in the GitHub issue is the difficulty of efficiently updating the version of WasmEdge in the documentation. The proposed solution is to use a general parameter called {{ wasmedge_version }} and update it to the latest version using a build step tool like 'sed'. This approach would simplify the process of maintaining and updating the version of WasmEdge in all the documentation files. Other suggestions include using versioning tools like Docusaurus and passing environment variables to Docusaurus V2.

        this result is generated by flows.network. Triggered by @alabulei1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

5 participants